Traceability Matrix for selected modules

Hi all,
We use DOORS 8.2

We have one UserReqs, one SystemSpec and below multiple SubSystemSpecs. For one SubSystemSpec I would like to have a traceability matrix in
that form:
UserReqs
System Spec
Specific Subsystem Spec
Specific Detailied Desing
The Analysis wizard provides me a list of ALL System Spec Requirement (even those that are not relevant for that specific SubsystemSpec).
Is there a way to alter the DXL code of the columns to have only those SystemSpec IDs displayed, that have also a link from the specific SubSystemSpec?

Thank you very much
Best Regards
Mathias Burchardt
B/E Aerospace Systems GmbH (formerly DAe Systems GmbH)
Mathias_Burchardt - Fri Jul 02 05:55:47 EDT 2010

Re: Traceability Matrix for selected modules
Ben_Sharples - Thu Jul 08 08:42:40 EDT 2010

which module are you running the analysis wizard from?

If you start the analayis wizard in the SubSystemSpec module you aer interested in it should only display the SystemSpec Objects that are linked to objects in the SubSystemSpec.

I'm assuming the link direction is the same way from each module, i.e.

UserReqs << SystemSpec << SubSystemSpec << DetailedDesign

You would want to run the analysis wizard twice once going to depth 2 in the driection of User Reqs to create the UserReqs and SystemSpec Columns and then re-run the analysis wizard in the opposite direction to get the DetailedDesign Column

Re: Traceability Matrix for selected modules
Mathias_Burchardt - Thu Jul 08 11:49:52 EDT 2010

Ben_Sharples - Thu Jul 08 08:42:40 EDT 2010
which module are you running the analysis wizard from?

If you start the analayis wizard in the SubSystemSpec module you aer interested in it should only display the SystemSpec Objects that are linked to objects in the SubSystemSpec.

I'm assuming the link direction is the same way from each module, i.e.

UserReqs << SystemSpec << SubSystemSpec << DetailedDesign

You would want to run the analysis wizard twice once going to depth 2 in the driection of User Reqs to create the UserReqs and SystemSpec Columns and then re-run the analysis wizard in the opposite direction to get the DetailedDesign Column

Thank you very much for your answer, Ben.
The way you proposed is what I thought on doing. But this would not create a real traceability tree, since one and the same User requirement ID, that is linked to multiple System Spec IDs, would then be listed multiple times in the "first row". Also we have heaps of other objects in the subsystem spec that are not of interest here, so the example I gave you was just very basic.
I rather thought on editing the current DXL output after running the Wizard making the IDs that have no children vanish from the output.
Best Regards,
Mathias

Re: Traceability Matrix for selected modules
Ben_Sharples - Fri Jul 09 06:13:48 EDT 2010

Mathias_Burchardt - Thu Jul 08 11:49:52 EDT 2010
Thank you very much for your answer, Ben.
The way you proposed is what I thought on doing. But this would not create a real traceability tree, since one and the same User requirement ID, that is linked to multiple System Spec IDs, would then be listed multiple times in the "first row". Also we have heaps of other objects in the subsystem spec that are not of interest here, so the example I gave you was just very basic.
I rather thought on editing the current DXL output after running the Wizard making the IDs that have no children vanish from the output.
Best Regards,
Mathias

If you write some dxl that checks if an object has any links to it (in or out) depending on your architecture before the display lines of the wizard code and put these inside an if that checks for a null resposne to the links.

dxl loop to check for links would be:
  

int i = 0
 
for lnk in o <- "*"  do {  // for outlinks
    i++
}
 
if (i > 0) {
   displayRich("\\pard " s)  // you will have a line like this in the wizard that displays the text
}

 


I'm using a counter to count the number of in-links(children) if this is 0 the display element of the wizard won't run